EVE Search - Oh my god, it's full of bugs :)

All Channels

Test Server Feedback

Oh my god, it's full of bugs :)

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Author	Thread Statistics \| Show CCP posts - 2 post(s)
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.09 20:43:00 - [1] To be honest, the current SiSi client is so full of bugs and the latest mirror is so weird, I'm not even sure where I should begin to explain it... or wether to make any bugreports at all. To name just a couple of things obvious from the first couple of minutes of fiddling around that are NOT yet listed on the "known issues" section of the "in testing" page: * all existing rigs were stripped away from ships * neural remapping DOESN'T stick - logout, log back in, you're back at your pre-remap attributes * the market shows every order as "range:system" regardless of location * fiting screen has no obvious close button (you can close it from the neocomm though) So... umm... I guess I'll wait a couple more days... weeks... or so, before I even start taking the stuff that's on SiSi seriously.
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.09 21:32:00 - [2] Originally by: Tunak How many of these bugs have made it from the TEST server to the PROD server? Oh none? Why are you crying chicken little? Ahem... I believe my main (and only) point was that the bugs are so many and so obvious that I am very reluctant to even CONSIDER bugreporting them, as I am VERY DOUBTFUL about the usefulness of making such bugreports at this particular stage. _ Create a character \|\| Fit a ship \|\| Get some ISK
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.09 21:44:00 - [3] Edited by: Akita T on 09/02/2009 21:45:24 Originally by: Tunak That's brialliant! Rather than acctually trying to help by filling out bug reports you'll just come here, the wrong forum for reporting issues with test, and rabble rouse! give two thumbs up to Akit Yes, because getting 2853 bugreports of "market shows all ranges as system", 754 bugreports of "my rigs are gone on SiSi" and 3987 bugreports of "neural remap doesn't work" WILL DO WONDERS FOR THE DEVELOPER AWARENESS OF THOSE BUGS, isn't it ? On the other hand, the few bugreports of SERIOUS game-affecting bugs that only a handful of players will encounter at this stage will be literally drowned in the sea of trivial bugreports. Trivial, as in "what the HELL do the guys in QA do anyway". P.S. In case that's not yet clear... Bugreporting now is pointless. You should wait with bugreports until after all bloody obvious bugs are out of the system, to avoid unnecessary clutter. At least, that's my viewpoint. _ Create a character \|\| Fit a ship \|\| Get some ISK
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.09 21:47:00 - [4] Edited by: Akita T on 09/02/2009 21:48:08 Originally by: Tunak Yeah just assume someone else will do the work. That way all you have to do is ****. gasp* I was just assuming people will do their jobs, what WAS I THINKING ?!?! Originally by: CCP Hypnotic All joking aside. I can see how you get that impression, but please don't let that discourage you from bug reporting. They really are useful. Worst case scenario, someone already reported it and it gets closed. No big deal. But someday you'll notice that one little thing nobody's seen before and you'll have saved the day. Then you'll feel all special with a nice warm glow inside. Who doesn't want to feel all warm inside? Like 98.6 degrees warm inside. That's very special. Yeah, but isn't getting thousands of duplicate bugreports a BAD thing for the guys handling the defect reports ? Wouldn't it be a much saner approach to wait until the obvious ones are ironed out first ?
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.09 21:53:00 - [5] Originally by: Ki Tarra You mean like the guy who found the boot.ini bug and didn't report it because he thought that something that obvious couldn't be published? I will start filing bug reports for the test server, when the bug reports that I file for the production server get handled. That reminds me of this... Bug report ID : 37908 Title : Deadspace NPCs still get MWD sigradius penality Description: While approaching a player ship from a distance, with afterburner-level speedboost (when previously, a long time ago, they would have used a MWD-level speedboost), the NPC rats in deadspaces still get a signature radius penality as if they were using MWDs even if they now only use afterburners. Build : Revelations 1.4.2 Reported : 2007.05.24 at 08:39:07 Official status : "Fixed in: WAR 1.1" REAL status : not fixed
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.09 21:59:00 - [6] Edited by: Akita T on 09/02/2009 22:00:14 Originally by: Tunak Originally by: Akita T Originally by: Tunak Yeah just assume someone else will do the work. That way all you have to do is ****. gasp* I was just assuming people will do their jobs, what WAS I THINKING ?!?! You weren't. You're job is to file bugreports. That's the point of test. Not to log in and *** about how things aren't ready for PROD. No ** that's why they're on test. I think you're confusing VOLUNTEER WORK with A PAYING JOB. And you are also confusing "I will never report any bugs" with "I will report bugs when the available build is stable enough".
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.10 09:42:00 - [7] Besides, what exactly should the bugreport read ? TITLE : Skill training and skill queue broken DESCRIPTION : Title says it all. Almost nothing really works. ... seriously ? Should I bugreport THAT ? _ Create a character \|\| Fit a ship \|\| Get some ISK
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.11 03:22:00 - [8] Originally by: LordSwift Originally by: SecHaul Originally by: LordSwift [...]But its more efficient to get the playerbase adding to the QA teams manpower to squash these bugs fast.[...] How is it more efficient to get the playerbase to identify bugs that are so obvious all you need to do is login an use the feature, and you instantly get hit with several? It's more efficient to get the playerbase to identify bugs when the manpower to find them exceeds the manpower to read through bug reports and forums, and right now I would argue a single person at CCP could identify 90% of the bugs simply by logging onto a PC at CCP and trying to use each feature once. [...] I'm sorry, but the state at which you should involve a larger beta test assumes the basics are done. And the basics are far from done. [...]But one person cannot find all the problems. It is more efficient to get more people bug hunting and get the reports in to ccp to fix. The issue is that we dont have a database to search previously submitted bugs. So we wont send a duplicate in. (Correct me if i am wrong) From previous experience in Games Testing, when we found a bug, we would search a database for a bug report. If their was one in their, we wouldnd report it again, except maybe add notes Well, one person can't find all problems, but problems so obvious that NOT ONLY are they obvious, but actually prevent any further testing... that's not something ready for a mass beta test yet... heck, I couldn't even call that alpha stage, it's pre-alpha, some kind of proof of concept (actually, not even that much). Only after those trivial-to-find bugs are fixed and features CAN actually function (at least to a limited degree) for most people, THEN you're ready for mass testing. The build which was available isn't even close enough to that, and bugreporting anything at this stage actually ADDS work to the dev team IMO. _ Create a character \|\| Fit a ship \|\| Get some ISK
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.11 05:47:00 - [9] Originally by: Roemy Schneider wait... first, there's (semi)huge threads about "when do we get to test apocaipirinha blahblah!!11eleven!1". then the result gets ***ed about, seven weeks before march comes to an end? Wasn't it supposed to go live on March 10th ? Ok, maybe it will be pushed back to the end of March. But by the looks of it, I'd say it will be pushed back to April, even late April. The underlying and self-understood thing in all the "waah waah apocrypha on SiSi nao plz" whines was that it would be a FUNCTIONAL build, and we would help with BALANCING and FINE-TUNING... not with pre-alpha bughunting. So, while I can appreciate the fact this pre-alpha build IS available for public testing, I can only repeat the same thing I've said before several times already : the state of the current build is "so obvious-bug-ridden" that BUGREPORTING any of them would be NEARLY pointless, at least at this particular stage**. After the obvious bugs are worked out, and features are at least SEEMINGLY functional at first sight... yeah, sure, THEN let's start with the bugreporting.
Akita T Caldari Navy Volunteer Task Force	Posted - 2009.02.11 16:59:00 - [10] Originally by: Gnulpie Since it is impossible to not detect those absolutely basic bugs and broken stuff, the only reasonable conclusion is, that they included these bugs on purpose. _ Create a character \|\| Fit a ship \|\| Get some ISK

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.